Skip to content

prun: Add documentation in markdown format #201

Merged
merged 6 commits into from
Aug 16, 2021
Merged

Conversation

thomas
Copy link
Contributor

@thomas thomas commented Aug 11, 2021

Manual pages can be generated with:

pandoc --standalone --to man prun.md -o prun.man.1

Manual pages can be generated with:

  pandoc --standalone --to man prun.md -o prun.man.1
@thomas
Copy link
Contributor Author

thomas commented Aug 11, 2021

Installation needs to be checked, since pandoc comes from a package.
Easiest would be to place the readymade man pages here too.

@donald
Copy link
Collaborator

donald commented Aug 11, 2021

Wow. Documentation! Very unusual, very good.

prun/prun.md Outdated
AUTHORS
=======

D.Buczek, P.Marquardt, M.Tolzmann
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I managed to do the 10 lines on my own. But I don't want to boast about it. Okay to leave out the credits section.

@donald
Copy link
Collaborator

donald commented Aug 12, 2021

Installation needs to be checked, since pandoc comes from a package.
Easiest would be to place the readymade man pages here too.

A "build" step ("make && make install") does not work here unless the compilation output is stable (identical on each build). If there was, for example, a comment with a timetag in the output, this would be a problem. mxtools doesn't have a global version number, so "make install" installs whatever is different from the installed version. Each "make install" of two people with the same checked out sources would install the semantically equal but binary different output files over each other every time.

We had that with a binary output and removed the program from mxtools for that reason ( #135 ). Another reason was that at that time the files installed by mxtools were not visible to bee query which is fixed now.

If the pandoc output is stable, I think we should just add a "make" phase to build the man pages. Why is it important that we have pandoc in a package? Its just a command, isn't it?

To check in the pandoc output... Well thats ugly. But if we don't have a better idea, we might do that.

prun/prun.md Outdated

The main usage is to run software in a specific version, or to provide a given environment. See **EXAMPLES** below.

There are some advantages over so called 'virtual environments' and the like. Packages are immutable, once installed they never change, thereby increasing the chances that an old program/script will also run in a few years. The packages also
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: dangling whitespace

@donald
Copy link
Collaborator

donald commented Aug 12, 2021

pandoc output seems to be stable. I've suggested build logic in #202.

@thomas
Copy link
Contributor Author

thomas commented Aug 12, 2021 via email

@thomas
Copy link
Contributor Author

thomas commented Aug 12, 2021 via email

@donald
Copy link
Collaborator

donald commented Aug 12, 2021

We could make make insist on not being root to make sure people use make as non-root before sudo make install .

@thomas
Copy link
Contributor Author

thomas commented Aug 12, 2021 via email

@donald
Copy link
Collaborator

donald commented Aug 12, 2021

Prun is a little bit like the tip of the iceberg of the whole package
machinery. My thought was to mention the main devs in this place.

Okay, I'm not aware of Peters and Marius' part, but I don't really care anyway. Leave it as it is. Sorry for bringing this up.

Use `-f` flag of `rm` to avoid error messages from `make clean` when the
targets files don't exist.
@donald
Copy link
Collaborator

donald commented Aug 12, 2021

I've added something to that "don't do that as root" effect to #202.

@thomas
Copy link
Contributor Author

thomas commented Aug 12, 2021 via email

@thomas
Copy link
Contributor Author

thomas commented Aug 12, 2021 via email

DESCRIPTION
===========

Similar to **type** or **which**. **ptype** gives information about a package binary. **type** would only tell something about the package wrapper, and not about the package where the real program is.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: dangling whitespace

@donald
Copy link
Collaborator

donald commented Aug 12, 2021

#202 is a PR to merge into this branch. So i think you can just press "merge" (and then "pulL" this branch into you local repository) if you want to include it.

@thomas
Copy link
Contributor Author

thomas commented Aug 12, 2021 via email

prun/pman.md Outdated
DESCRIPTION
===========

**ptype** uses the PATH set in the package wrapper and tries to find a manual page in the package directory.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean pman here instead of ptype?

Add build/install logic for prun manpages
Remove authors from prun.md, reformat
Remove copy-and-paste errors in pman.md
@thomas
Copy link
Contributor Author

thomas commented Aug 16, 2021

make; make install works well.

@thomas thomas merged commit 3772773 into master Aug 16, 2021
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants